Skip to main content

This is a new service – your feedback will help us to improve it.

Bristol City Council

Tree preservation zone

There is a problem

  • 368 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

Brentry Hospital Charlton Road Brentry Bristol BS10 6JH

reference
IBJE4DDNBB000
name
Brentry Hospital Charlton Road Brentry Bristol BS10 6JH
tree-preservation-order

undefined

355
tree-preservation-zone-type
group
geometry
MULTIPOLYGON (((-2.613612 51.503403,-2.613550 51.503419,-2.613520 51.503438,-2.613485 51.503465,-2.613471 51.503481,-2.613472 51.503497,-2.613493 51.503530,-2.613500 51.503544,-2.613559 51.503606,-2.613566 51.503626,-2.613610 51.503671,-2.613678 51.503733,-2.613709 51.503735,-2.613722 51.503731,-2.613742 51.503744,-2.613777 51.503744,-2.613798 51.503785,-2.613807 51.503814,-2.613799 51.503848,-2.613810 51.503897,-2.613803 51.503911,-2.613810 51.503957,-2.613805 51.504019,-2.613811 51.504045,-2.613819 51.504104,-2.613797 51.504188,-2.613801 51.504198,-2.613814 51.504215,-2.613799 51.504216,-2.613715 51.504211,-2.613690 51.504211,-2.613670 51.504204,-2.613520 51.504210,-2.613461 51.504227,-2.613426 51.504248,-2.613391 51.504282,-2.613386 51.504293,-2.613374 51.504311,-2.613341 51.504328,-2.613307 51.504356,-2.613230 51.504385,-2.613136 51.504415,-2.613024 51.504447,-2.612937 51.504470,-2.612750 51.504527,-2.612700 51.504548,-2.612611 51.504644,-2.612526 51.504694,-2.612498 51.504707,-2.612469 51.504726,-2.612463 51.504740,-2.612476 51.504750,-2.612457 51.504749,-2.612441 51.504769,-2.612417 51.504788,-2.612394 51.504801,-2.612359 51.504830,-2.612350 51.504834,-2.612344 51.504840,-2.612396 51.504845,-2.612415 51.504856,-2.612494 51.504874,-2.612515 51.504890,-2.612605 51.504910,-2.612651 51.504909,-2.612684 51.504906,-2.612715 51.504898,-2.612754 51.504892,-2.612810 51.504871,-2.612833 51.504849,-2.612853 51.504840,-2.612884 51.504831,-2.612919 51.504817,-2.612934 51.504801,-2.612999 51.504770,-2.613015 51.504763,-2.613041 51.504763,-2.613154 51.504706,-2.613209 51.504686,-2.613274 51.504659,-2.613433 51.504607,-2.613461 51.504602,-2.613516 51.504589,-2.613572 51.504566,-2.613594 51.504578,-2.613642 51.504572,-2.613668 51.504566,-2.613706 51.504565,-2.613720 51.504571,-2.613749 51.504571,-2.613801 51.504579,-2.613939 51.504595,-2.614009 51.504608,-2.614051 51.504604,-2.614199 51.504622,-2.614271 51.504600,-2.614299 51.504596,-2.614330 51.504585,-2.614327 51.504545,-2.614303 51.504528,-2.614246 51.504479,-2.614235 51.504465,-2.614233 51.504441,-2.614290 51.504423,-2.614319 51.504412,-2.614264 51.504299,-2.614286 51.504297,-2.614349 51.504264,-2.614364 51.504250,-2.614408 51.504232,-2.614423 51.504208,-2.614420 51.504200,-2.614408 51.504194,-2.614423 51.504187,-2.614400 51.504162,-2.614399 51.504149,-2.614430 51.504147,-2.614453 51.504136,-2.614476 51.504130,-2.614496 51.504117,-2.614467 51.504091,-2.614388 51.504032,-2.614368 51.504012,-2.614343 51.504001,-2.614303 51.503968,-2.614292 51.503958,-2.614274 51.503936,-2.614224 51.503895,-2.614116 51.503796,-2.614102 51.503776,-2.614051 51.503737,-2.614010 51.503734,-2.613988 51.503719,-2.613978 51.503705,-2.613946 51.503704,-2.613959 51.503691,-2.613942 51.503663,-2.613952 51.503638,-2.613875 51.503537,-2.613857 51.503533,-2.613823 51.503501,-2.613809 51.503479,-2.613784 51.503434,-2.613761 51.503431,-2.613751 51.503418,-2.613712 51.503416,-2.613664 51.503400,-2.613612 51.503403)))
point
POINT (-2.613621 51.504285)
notes
MONTEREY CYPRESS - Cupressus macrocarpa,BEECH - Fagus sylvatica,WALNUT - Juglans regia,ENGLISH OAK - Quercus robur,LAWSON CYPRESS - Chamaecyparis lawsoniana,SCOTS PINE - Pinus sylvestris,SYCAMORE - Acer pseudoplatanus,NORWAY SPRUCE - Picea
entry-date
2005-02-07
start-date
2005-02-07
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Bristol City Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL